Previous Next Tracker index See it online !

(20/185) 42 - Make Sidekick mode a buffer-local property

I would appreciate, if the side kick "AutoParseSettings"
would be available as buffer-local-property.

I am working with various modes (Ruby, XML, Shell, Perl), and it makes no sense to have the same AutoParseSettings for everyone. For instance, XML files often adhere to the XML Schema over a long time, so I don't want to have "auto-parse" there at all; on Ruby however, I would like
to have auto-parse at least on buffer change and file save.

I understand that it is not possible to set auto-parse
on a per file mode (although this too would be helpful),
but at least having it definable as buffer-local property
would be helpful.

Ronald

Submitted	rovf - 2007-08-07 14:58:44	Assigned
Priority	5	Labels
Status	open	Group	None
Resolution	None

Comments

2007-08-07 16:03:16 ezust	Logged In: YES user_id=935841 Originator: NO I could make it a "mode property" settable from the sidekick dockable mode properties dialog. Would that be better?
2007-08-08 07:47:18 rovf	Logged In: YES user_id=1168843 Originator: YES A mode property would for sure be \very\ helpful indeed\!\!\! But I would like to point out that this is kind of an "orthogonal solution" to my proposal, in that one complements, instead of obviates the other. For instance, 90% of my XML files conform to some XML schema while 10% deliberately do not (for testing purposes), and the main reason why I had switched off automatic parsing by Sidekick, is that is annoying to always have the error list being popped up on those 10%. So if I had both - mode property and buffer local settings -, I would set "auto-parse on buffer switch and save" for XML files (mode-property setting) and manually switch this off for those few files which should not be parsed (buffer-local setting). Do you think this can easily be done both? If I were forced to decide on only one solution - mode property or buffer local -, I think the buffer local settings would be more useful. If people, working with several languages, want to have one type of parsing strategy with one mode, they likely want to have the same with the other modes as well, so the "exceptions from the default" are probably more often file-based than mode based.
2007-08-08 07:57:01 kpouer	Logged In: YES user_id=285591 Originator: NO Hi, what happens to the user mode properties when a mode is reloaded ?